Sams Teach Yourself MCSE Windows NT Server 4 in 14 Days
(Publisher: Macmillan Computer Publishing)
Author(s): David Schaer, et al
ISBN: 0672311283
Publication Date: 12/15/97

You can select one or multiple protocols at this time. Figure 3.25 shows the protocol selection screen.

Figure 3.25.  Initial protocol selection is made.

Select TCP/IP when there is a need for connection to the Internet or when systems must communicate over an IP-routed network. NWLINK, or NetWare Link, is compatible with Novell’s IPX/SPX protocol. It can be used on a routed network whether or not a NetWare server is present. NetBEUI (Network Basic Enhanced User Interface) is a very fast protocol for use on single segments of a network. NetBEUI is not a routable protocol; it can, like all other protocols, be bridged. If the computer being installed is a BDC you must select at least one protocol that is also in use on the PDC.

In addition to the basic network services shown in Figure 3.26, you can also select to install advanced services at this time. Advanced services include DHCP Server, Remote Access Server, DNS server, and others, which are discussed in Chapter 11.

Figure 3.26.  Selecting the basic network services.

After you select the services you must configure protocol settings for TCP/IP or IPX/SPX, if either were selected. If you have selected to install the DHCP Server service on the system you must configure TCP/IP manually; a DHCP server cannot be a DHCP client. NetBEUI is self-configuring.

The protocol bindings are displayed in Figure 3.27. You can change the binding order and thus the priority of the protocols relative to specific services.

Figure 3.27.  The protocol binding order.

The system now initializes the network.

When installing a PDC the name of the domain being created is required. Figure 3.28 shows NTMASTER being installed as the PDC for the KNOWLEDGE domain.

Figure 3.28.  NTMASTER is configured as the PDC for KNOWLEDGE.

Enter the appropriate time zone. Figure 3.29 shows the system configured for GMT+01:00.

Figure 3.29.  Enter the time zone information.

The system displays the video information and requires that you test the video configuration before continuing. In Figure 3.30 the video configuration is displayed.

Figure 3.30.  Configuring the system video.

If the video does not appear properly during the test mode simply wait until the test completes and try a different configuration.

The final step is to create the emergency repair disk if the option was selected. The emergency repair disk only reflects the system configuration at the time of installation unless it is periodically updated using the Repair Disk utility, RDISK.EXE. The emergency repair disk should be updated following any major system change including hardware, software, and user configuration.

The BOOT.INI is updated to reflect the new installation of NT as the default boot selection.

The installation is now complete.

3.6. Hands-Free Installations

Several methods are available to perform hands-free installations. The most common method is by utilizing the NT Setup Manager to create text-based answer files. The answer files are called during over-the-network installation when the /u and /s switches are employed.

The NT installation can also be activated through Microsoft Systems Management Server or by something as simple as a batch file called in a logon script.

Microsoft System Management Server can be used to force or push the installation of various software packages to the target system. For example, a package containing Microsoft Office 97 could be distributed and installed on the client machine. Not all software packages provide a script that lets SMS perform an automated installation.

The sysdiff.exe utility allows an installation of NT to be enhanced by including additional software. The software installed using sysdiff.exe does not have to support scripting. In essence, the sysdiff.exe utility creates a file containing system differences between a clean target machine and the same machine after desired software has been installed. The difference file can be applied to other target machines to lay down the software and update the registry. Hardware and software resellers use the sysdiff.exe utility most commonly.

3.7. Uninstalling Windows NT

If you loaded NT for trial purposes, or if you want to turn a stand-alone or member server into a controller, removing it at some point might be necessary. Uninstalling NT, without losing other applications or data, requires only a few simple steps.

If NT was installed on a FAT partition, simply boot into DOS or Windows 95 either from a system disk or by selecting the other operating system on multiboot machines. A system disk is a better choice because it is often necessary to SYS the drive.

Next, delete the entire Windows NT directory structure from the %SYSTEM_ROOT% down.

Finally, delete the file pagefile.sys and all system files in the root of the system partition, including NTLDR, NTDETECT.COM, BOOTSECT.DOS, BOOT.INI, and—if it exists—NTBOOTDD.SYS.

If NT is installed on an NTFS partition and another copy of NT is installed in another directory, delete the unwanted NT installation manually. The BOOT.INI file must be manually updated to note the removal.

If NT is installed as the only operating system on an NTFS partition, remove it by deleting the partition (the setup disks can be used for this).

3.8. Selecting Network Protocols

The exams will test your knowledge of four basic network protocols: TCP/IP, NWLink (IPX/SPX), NetBEUI, and DLC. Remember to focus on what each protocol has in common and at the same time what features make each protocol unique.

3.8.1. TCP/IP

TCP/IP has been popularized within NT and Microsoft exams. TCP/IP has gained so much popularity over the years for several reasons:

•  TCP/IP is a routable protocol.

•  TCP/IP is the protocol the Internet uses.

•  TCP/IP is a common protocol implemented by all major network manufacturers.

3.8.2. NWLink (IPX/SPX)

NWLink is Microsoft’simple mentation that is compatible with Novell’s implementation of IPX/SPX. Although the name implies that the sole purpose of NWLink is to connect to NetWare servers, that is not the case. In fact, NWLink may be the protocol running on a pure NT network. Also, NWLink without either Client Services for NetWare (CSNW) or Gateway Services for NetWare (GSNW) loaded would allow access to a NetWare application server (such as Oracle or Sybase running as an NLM).